chore: fix JavaScript lint errors (issue #8593) #8595
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
status: passed
status: passed
status: na
status: na
status: na
status: passed
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: na
status: passed
status: na
status: passed
Resolves #8593.
Description
This pull request fixes JavaScript linting errors detected in the automated lint workflow.
The main issues were:
@stdlib/_tools/github/create-repothat triggered real GitHub API requests during linting.This PR updates these files to ensure that all JavaScript lint tasks pass reliably without executing network requests or failing doctest parsing.
Related Issues
Questions
No.
Other
No additional notes.
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
This format of PR was developed with the assistance of ChatGPT .
@stdlib-js/reviewers